The FAIR Guiding Principles for scientific data management and stewardship

There is an urgent need to improve the infrastructure supporting the reuse of scholarly data. A diverse set of stakeholders—representing academia, industry, funding agencies, and scholarly publishers—have come together to design and jointly endorse a concise and measureable set of principles that we refer to as the FAIR Data Principles. The intent is that these may act as a guideline for those wishing to enhance the reusability of their data holdings. Distinct from peer initiatives that focus on the human scholar, the FAIR Principles put specific emphasis on enhancing the ability of machines to automatically find and use the data, in addition to supporting its reuse by individuals. This Comment is the first formal publication of the FAIR Principles, and includes the rationale behind them, and some exemplar implementations in the community

Kitware/vtk-js: v28.11.0

28.11.0 (2023-09-12) Bug Fixes PickerManipulator: add setPicker function (80926db) PickerManipulator: declare types for get/set picker methods (2f06de3) PickerManipulator: move macro.setGet to extend function (25cec02) PickerManipulator: move default picker definition to defaultValues (46917a9) PickerManipulator: remove addActor and setTolerance from API (3e4fe8b) PickerManipulator: replace automatic relative import with absolute import (4fd1893) PickerManipulator: return null instead of origin when picked position is undefined (14a8c46) PickerManipulator: use macro.setGet to define setter and getter (220e2b9) PickerManipulator: use relative import (4df091a) SeedWidget: add direction mixin (f799d35) SeedWidget: demonstrate how to change handle color (69386b2) SeedWidget: move classHierarchy.push to top of widgetBehavior (7997b8e) SeedWidget: move direction initial value definition (1a19b42) SeedWidget: refer to model.widgetState directly in widgetBehavior (feda6cf) SeedWidget: set initial direction to [0, 0, 1] (42b51d5) Features ActorPickManipulator: constrain handle movement to actor surfaces (ad1c9b9) SeedWidget: a single-handle widget that can be placed and replaced (767901e

An approximate Bayesian significance test for genomic evaluations

Genomic information can be used to study the genetic architecture of some trait. Not only the size of the genetic effect captured by molecular markers and their position on the genome but also the mode of inheritance, which might be additive or dominant, and the presence of interactions are interesting parameters. When searching for interacting loci, estimating the effect size and determining the significant marker pairs increases the computational burden in terms of speed and memory allocation dramatically. This study revisits a rapid Bayesian approach (fastbayes). As a novel contribution, a measure of evidence is derived to select markers with effect significantly different from zero. It is based on the credibility of the highest posterior density interval next to zero in a marginalized manner. This methodology is applied to simulated data resembling a dairy cattle population in order to verify the sensitivity of testing for a given range of type‐I error levels. A real data application complements this study. Sensitivity and specificity of fastbayes were similar to a variational Bayesian method, and a further reduction of computing time could be achieved. More than 50% of the simulated causative variants were identified. The most complex model containing different kinds of genetic effects and their pairwise interactions yielded the best outcome over a range of type‐I error levels. The validation study showed that fastbayes is a dual‐purpose tool for genomic inferences – it is applicable to predict future outcome of not‐yet phenotyped individuals with high precision as well as to estimate and test single‐marker effects. Furthermore, it allows the estimation of billions of interaction effects

Kitware/vtk-js: v29.0.0

<h1><a href="https://github.com/Kitware/vtk-js/compare/v28.13.1...v29.0.0">29.0.0</a> (2023-10-26)</h1> <h3>Bug Fixes</h3> <ul> <li><strong>genericrenderwindow:</strong> support WebGPU backend (<a href="https://github.com/Kitware/vtk-js/commit/8b6cc9f3352f068e4312b0bd871243285f4cfc51">8b6cc9f</a>)</li> <li><strong>vtkwebxrrenderwindowhelper:</strong> Replace global XRGLLayer definition (<a href="https://github.com/Kitware/vtk-js/commit/6bcfa21a9eba4219519f5fca81f490c9dbc4179d">6bcfa21</a>)</li> <li><strong>webgpu:</strong> expose onWindowResizeEvent function to render window WebGPU backend (<a href="https://github.com/Kitware/vtk-js/commit/7f33beb4a9d2776fa42a740164b1d1850c1c25f2">7f33beb</a>)</li> <li><strong>widgetmanager:</strong> support WebGPU captureBuffer (<a href="https://github.com/Kitware/vtk-js/commit/aa0332de3121c5962047d70a5f257c13e980a887">aa0332d</a>)</li> </ul> <h3>Code Refactoring</h3> <ul> <li>drop DistanceWidget (<a href="https://github.com/Kitware/vtk-js/commit/31b1b930b98aebf82a83530c732be0838d80318a">31b1b93</a>)</li> <li><strong>webxrrenderwindowhelper:</strong> refactor WebXR rendering support (<a href="https://github.com/Kitware/vtk-js/commit/2e7a9c7a25954d9dd4d2ec11d9906c949ded4d8b">2e7a9c7</a>)</li> </ul> <h3>Features</h3> <ul> <li>setSize triggers WindowResizeEvent (<a href="https://github.com/Kitware/vtk-js/commit/80073dc2ed4667a3ae0f1d30b2fd6439ced9a8ec">80073dc</a>)</li> <li><strong>vtkwebxrrenderwindowhelper:</strong> update helper class interface for application logic (<a href="https://github.com/Kitware/vtk-js/commit/3a862165e6bf4bbc959cce8b9e974fa8a1324d40">3a86216</a>)</li> <li><strong>WidgetManager:</strong> remove deprecated APIs (<a href="https://github.com/Kitware/vtk-js/commit/603d4f1fd8c37033382175c0d2e85cdac5254670">603d4f1</a>)</li> </ul> <h3>BREAKING CHANGES</h3> <ul> <li>LineWidget is favored over the distance widget.</li> <li><strong>WidgetManager:</strong> remove deprecated widget manager APIs</li> <li><strong>webxrrenderwindowhelper:</strong> Removes WebXR API from <code>vtkOpenGLRenderWindow</code>. Applications requiring XR support must instantiate <code>vtkWebXRRenderWindowHelper</code> instead.</li> </ul&gt